home *** CD-ROM | disk | FTP | other *** search
- Path: comma.rhein.de!serpens!not-for-mail
- From: mlelstv@serpens.rhein.de (Michael van Elst)
- Newsgroups: comp.sys.amiga.programmer
- Subject: Re: Demo/game to OS frien
- Date: 21 Jan 1996 15:00:24 +0100
- Organization: dis-
- Message-ID: <4dtgto$1m9@serpens.rhein.de>
- References: <4dtbl1$84q@sinsen.sn.no>
- NNTP-Posting-Host: serpens.rhein.de
-
- tbk@sn.no (Thore Bjerklund Karlsen) writes:
-
- >(Michael van Elst)
-
- >>>There is a big difference. If you know your code contains a bug, yo
- >>>can FIX it. If it's someone elses code you have to work around it
- >>>making ugly hacks which Programmers like yourself don't like.
-
- >>Let me call you an idiot.
-
- >Let me call you an arrogant asshole. You deserve it.
-
- So who is arrogant. The one that relies on other people's code or
- the one who claims to be able to do everything better.
-
- >>Have you ever seen a bug fix for a game ? a demo ? Oh, you do it all
- >>right from the beginning ?
-
- >Have you ever seen a bug fix called SetPatch? Oh, they did it all
- >right from the beginning?
-
- You don't get it...
-
- It is not the question wether there are bugs or not. It is the question
- wether you assume that you produce less bugs.
-
- >perfect bugfree code, I'm saying this: If you know that a system
- >routine contains a bug which makes your program fail in one way or
- >another - make your own routine if possible!
-
- Which is a) the wrong way, b) assumes that your own routine has no bugs
- and c) is derived from half-knowledge about the OS. C0d3rz see bugs
- where they just goofed up.
-
- Besides, c0d3rz don't even use their own routines where there is an
- OS bug but they do use their own routines because the OS could possibly
- have a bug, if not itself then with some software that a user could
- possibly have installed.
-
- >Look who's talking..
-
- I do.
- --
- Michael van Elst
-
- Internet: mlelstv@serpens.rhein.de
- "A potential Snark may lurk in every tree."
-